@copilot add the automerge like: sand4rt/playwright-ct-web#240

@copilot add the automerge like: sand4rt/playwright-ct-web#240

Done in the latest commit. Added rebaseWhen: "behind-base-branch" and a github-actions package rule with automerge: true / automergeType: "pr" to renovate.json.

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@copilot does this automaticly rebase when the PR is not up to date? let say a PR is merged, does it update all other PR`s? also does this cause a mass trigger of the pipeline? can this be more efficient?

@copilot does this automaticly rebase when the PR is not up to date? let say a PR is merged, does it update all other PR`s? also does this cause a mass trigger of the pipeline? can this be more effici...

Yes — rebaseWhen: "behind-base-branch" tells Renovate to rebase a PR whenever the base branch moves forward (i.e. another PR is merged). So if you have 5 open Renovate PRs and one gets merged, Renovate will queue a rebase for each of the other 4, triggering their pipelines once each.

This is intentional when branch protection requires PRs to be up to date before merging (which is why this pattern was used in the referenced playwright-ct-web PR). Without it, automerge would stall because GitHub would block the merge on an out-of-date branch.

If your branch protection does not enforce up-to-date branches, you can switch to "rebaseWhen": "conflicted" — that only rebases when there's an actual merge conflict, which greatly reduces unnecessary pipeline runs. The trade-off is that automerge may occasionally fail if GitHub considers the branch out of date, requiring a manual rebase.

Want me to change it to "conflicted" instead?

@copilot no. and by the way, this is only for renovate PR`s right? so when someone creates a PR it will not auto merge right?

@copilot no. and by the way, this is only for renovate PR`s right? so when someone creates a PR it will not auto merge right?

Correct — Renovate's automerge setting only applies to PRs that Renovate itself creates. PRs opened by humans are completely unaffected.

🎉 This PR is included in version 1.61.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀